Method and system for detecting edge server in mobile telecommunication network

ABSTRACT

The present disclosure relates to a communication method and system for converging a 5th-Generation communication system for supporting higher data rates beyond a 4th-Generation system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The present disclosure describes a method and a system for detecting Enhanced Data rates for Global System for Mobile (GSM) Evolution (EDGE) server in a mobile telecommunication network by a mobile terminal.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is based on and claims priority under 35 U.S.C. §119(a) to Indian Provisional Patent Application No. 201841037842 (PS),filed in the Indian Patent Office on Oct. 5, 2018 and to IndianNon-Provisional Patent Application No. 201841037842 (CS), filed in theIndian Patent Office on Oct. 4, 2019, the entire disclosure of each ofwhich is incorporated herein reference.

BACKGROUND OF THE INVENTION Field of the Invention

The present disclosure generally relates to field of telecommunicationnetwork. Particularly, but not exclusively, the present disclosurerelates to a method and a system to detect Enhanced Data rates forGlobal System for Mobile (GSM) Evolution (EDGE) server in a mobiletelecommunication network for efficient packet routing.

Description of the Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems, efforts have been made todevelop an improved 5G or pre-5G communication system. Therefore, the 5Gor pre-5G communication system is also called a ‘Beyond 4G Network’ or a‘Post LTE System’. The 5G communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, soas to accomplish higher data rates. To decrease propagation loss of theradio waves and increase the transmission distance, the beamforming,massive multiple-input multiple-output (MIMO), Full Dimensional MIMO(FD-MIMO), array antenna, an analog beam forming, large scale antennatechniques are discussed in 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud Radio Access Networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,Coordinated Multi-Points (CoMP), reception-end interference cancellationand the like. In the 5G system, Hybrid FSK and QAM Modulation (FQAM) andsliding window superposition coding (SWSC) as an advanced codingmodulation (ACM), and filter bank multi carrier (FBMC), non-orthogonalmultiple access (NOMA), and sparse code multiple access (SCMA) as anadvanced access technology have been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof Things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofEverything (IoE), which is a combination of the IoT technology and theBig Data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “Security technology” have been demanded forIoT implementation, a sensor network, a Machine-to-Machine (M2M)communication, Machine Type Communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing Information Technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, Machine Type Communication (MTC), andMachine-to-Machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RadioAccess Network (RAN) as the above-described Big Data processingtechnology may also be considered to be as an example of convergencebetween the 5G technology and the IoT technology.

The information disclosed in this background of the disclosure sectionis only for enhancement of understanding of the general background ofthe invention and should not be taken as an acknowledgement or any formof suggestion that this information forms the prior art already known toa person skilled in the art.

SUMMARY OF THE INVENTION

In an embodiment, the present disclosure may relate to a method fordetecting EDGE server in a mobile telecommunication network by a mobileterminal. The method comprising transmitting, by the mobile terminal, aregistration request to a base station, receiving, by the mobileterminal, a registration accept response from the base station, whereinthe registration accept response comprises LADN information, sending, bythe mobile terminal, a Domain Name Server (DNS) query using the LADNinformation to a DNS operator, receiving, by the mobile terminal, an IPaddress of a MEC server in response to the DNS query, registering, bythe mobile terminal, mobile terminal information with the MEC serverusing the IP address and receiving, by the mobile terminal, informationon EDGE infrastructure availability and application server instancesfrom the MEC server.

In an embodiment, the present disclosure may relate to a mobile terminalfor detecting EDGE server in a mobile telecommunication network. Themobile terminal comprising a processor and a memory communicativelycoupled to the processor, wherein the memory stores processor-executableinstructions, which on execution, cause the processor to transmit aregistration request to a base station, receive a registration acceptresponse from the base station, wherein the registration accept responsecomprises LADN information, send a DNS query using the LADN informationto a DNS operator, receive an IP address of a MEC server in response tothe DNS query, register mobile terminal information with the MEC serverusing the IP address and receive information on EDGE infrastructureavailability and application server instances from the MEC server.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate exemplary embodiments and togetherwith the description, serve to explain the disclosed principles. In thefigures, the left-most digit(s) of a reference number identifies thefigure in which the reference number first appears. The same numbers areused throughout the figures to reference like features and components.Some embodiments of system and/or methods in accordance with embodimentsof the present subject matter are now described below, by way of exampleonly, and with reference to the accompanying figures.

FIG. 1A and FIG. 1B illustrate an exemplary environment for trackingEDGE server by a mobile terminal in a mobile telecommunication networkin accordance with some embodiments of the present disclosure.

FIG. 2 shows a block diagram of an architecture of mobile enablementlayer in a mobile terminal in accordance with some embodiments of thepresent disclosure.

FIG. 3A and FIG. 3B illustrate sequence diagrams explaining operation ofregistration with EDGE server and service discovery by a mobile terminalin a mobile telecommunication network in accordance with someembodiments of the present disclosure.

FIG. 3C illustrates service level granularity in a mobiletelecommunication network in accordance with some embodiments of thepresent disclosure.

FIG. 4 shows a sequence diagram illustrating operation of DNS resolutionand packet routing in a mobile telecommunication network in accordancewith some embodiments of the present disclosure.

FIG. 5 illustrates a sequence diagram explaining operation of verifyinguser location using MEC server in a mobile telecommunication network inaccordance with some embodiments of present disclosure.

FIG. 6 shows a sequence diagram illustrating operation of Access PointName (APN) management and packet routing in a mobile telecommunicationnetwork in accordance with some embodiments of the present disclosure.

FIG. 7 illustrates LADN information provided with a “RegistrationAccept” message in accordance with some embodiments of the presentdisclosure.

It should be appreciated by those skilled in the art that any blockdiagrams herein represent conceptual views of illustrative systemsembodying the principles of the present subject matter. Similarly, itwill be appreciated that any flowcharts, flow diagrams, state transitiondiagrams, pseudo code, and the like represent various processes whichmay be substantially represented in computer readable medium andexecuted by a computer or processor, whether or not such computer orprocessor is explicitly shown.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

In the present document, the word “exemplary” is used herein to mean“serving as an example, instance, or illustration.” Any embodiment orimplementation of the present subject matter described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments.

While the disclosure is susceptible to various modifications andalternative forms, specific embodiment thereof has been shown by way ofexample in the drawings and will be described in detail below. It shouldbe understood, however that it is not intended to limit the disclosureto the particular forms disclosed, but on the contrary, the disclosureis to cover all modifications, equivalents, and alternatives fallingwithin the scope of the disclosure.

The terms “comprises”, “comprising”, or any other variations thereof,are intended to cover a non-exclusive inclusion, such that a setup,device or method that comprises a list of components or steps does notinclude only those components or steps but may include other componentsor steps not expressly listed or inherent to such setup or device ormethod. In other words, one or more elements in a system or apparatusproceeded by “comprises . . . a” does not, without more constraints,preclude the existence of other elements or additional elements in thesystem or method.

In the following detailed description of the embodiments of thedisclosure, reference is made to the accompanying drawings that form apart hereof, and in which are shown by way of illustration specificembodiments in which the disclosure may be practiced. These embodimentsare described in sufficient detail to enable those skilled in the art topractice the disclosure, and it is to be understood that otherembodiments may be utilized and that changes may be made withoutdeparting from the scope of the present disclosure. The followingdescription is, therefore, not to be taken in a limiting sense.

Mobile Edge Computing (MEC) enables cloud computing and InformationTechnology (IT) service environment at the edge of the network. In MEC,by running applications and performing application-related processingtasks closer to customer network, network congestion is reduced, andapplications perform better. As an example, the applications mayinclude, but are not limited to, gaming application, applicationsrelated to virtual/augmented reality and the like. The MEC isimplemented at cellular base stations or at other edge nodes and enablesflexible and rapid deployment of new applications and services forcustomers. MEC aims to place computing and storage resources in 4G/5GRadio Access Network (RAN) to improve delivery of content andapplications to end-users. The MEC technology enables operators to adaptbetter to the network traffic prevailing in the radio conditions,optimize service quality and improve network efficiency.

At present, to make applications agnostic to Enhanced Data rates for GSMEvolution (EDGE) deployment, 3rd Generation Partnership Project (3GPP) &European Telecommunications Standards Institute (ETSI) standards havedefined procedures for making User Equipment (UE) to be aware about EDGEavailability in a geographical area and have provision to route thepackets automatically to remote server or EDGE cloud server. In order tomake the UE aware about the EDGE deployed in the area, 5G registrationaccept may carry LADN (Local Area Data Network) information. However, inreality, not all cells of LADN would be EDGE deployed or EDGE could bedeployed along with few existing 4G RAN. Even if EDGE is deployed for aparticular application, due to resource restriction, some users may bepushed out of EDGE services temporarily. Hence, those application mayhave to connect to remote cloud automatically.

Further, in order to route the application packets to either EDGE orremote cloud, 3GPP has defined few mechanisms as described below.

Usage of Uplink Classifier (UL CL) functionality for a Protocol DataUnit (PDU) session. In this approach, the UL CL applies filtering rules(for example, to examine the destination Internet Protocol (IP) addressof IP packets sent by the UE) and determines how the packet should berouted. The drawback of this mechanism is that the UE uses the same IPaddress to access the network and is not aware with which Data Network(DN) it is communicating with.

Usage of an Internet Protocol version 6 (IPv6) multi-homing for a PDUsession. In this approach, a given PDU session is associated withmultiple IPv6 prefixes. A “common” user plane function referred to as“branching point” is responsible for steering the UL traffic towards oneor the other IP anchor based on the source prefix of the packet. Thebranching point for a given PDU session may be inserted or removed bythe Session Management Control Function (SMF) dynamically. Request ForComments (RFC 4191) is used to configure rules into the UE to influencethe selection of the source address.

Support for LADN. In this approach, the UE explicitly requests a PDUsession to a special Access Point Network/Digital Data Network (APN/DDN)in order to get access to the locally provided service. To support this,the Access and Mobility Management Function (AMF) provides to the UE theLADN information about the LADN availability. The AMF tracks the UE andinforms the SMF whether the UE is in the LADN service area. LADNinformation is provided to the UE by the AMF during registration. Thisinformation consists of LADN DNN and LADN service area information. TheUE may then request a PDU session establishment for an available LADNwhen the UE is located in the LADN service area.

In addition to 3GPP mechanisms illustrated above, at RAN level, networkcan implement deep packet inspection to route the packets. However, itis a costly operation and may not be a feasible solution when deployedat a large scale. All of the 3GPP mentioned mechanisms are mainlyconsidered to be deployed later i.e. after 5G network launch. But withthe existing 4G network or initial 5G launch, UE side implementation ofrouting packets to appropriate cloud needs to be taken care at thedevice side itself.

Embodiments of the present disclosure relate to a method and a systemfor EDGE server in a mobile telecommunication network by a mobileterminal. Typically, MEC server aims to compute and place storageresources in the 4G/5G radio access network to improve the delivery ofcontent and applications to end-users. Applications may includeself-driving, gaming, virtual/augmented reality, remote tele-surgery,etc. However, with the existing 4G network or initial 5G launch, userequipment side implementation of routing packets to appropriate MECserver needs to be taken care at the device side itself. The presentdisclosure provides a method that detects the deployment of MEC serverby way of polling for EDGE at geographical area change or periodically,and route application layer packets to remote server or EDGE server,based on whether application server resides in remote server or EDGEserver. The present disclosure provides an efficient mechanism forrouting data packets in telecommunication network based on determiningwhether application server resides in remote server or EDGE server.

FIG. 1A and FIG. 1B illustrate an exemplary environment for trackingEDGE server by a mobile terminal in a mobile telecommunication networkin accordance with some embodiments of the present disclosure.

As shown in the FIG. 1A, the environment includes a mobile terminal 100,an EDGE Infra 151 and a plurality of base stations 101, 103, 105, 107,109 and 111. The mobile terminal 100 may, also, be referred as aterminal, a mobile or a user equipment. Here, the EDGE Infra (also,referred as EDGE Infrastructure) 151 may refer to an EDGE serve or a MECserver or an LCM proxy or an EDGE Service Provider (ESP). The EDGE Infrahost application server instances using private IP addresses, which arenot accessible globally whereas DNS servers (not shown in FIG. 1A)provide public IP addresses for application server and cannot providethe nearest server instance such as the EDGE Infra. The base station maybe an evolved Node B (eNodeB) for 4G cellular network or a NextGeneration Node B (gNodeB) for 5G cellular network or a base stationsupporting 2G and/or 3G technology. The base stations 101, 103 and 105form a Tracking Area (TA). TA is basically a geographical combination ofseveral base stations (eNodeBs or gNodeBs). TA may be uniquelyidentified by a code called a Tracking Area Code (TAC). The basestations 101, 103 and 105 are identified by TAC 15. The base stations101, 103 and 105 together form a cell C1. Furthermore, the base station100, 103 and 105 may be identified by cell identifier (cid) 101, 103 and105, respectively. Here, in this application reference numerals of thebase stations and respective cell identifiers (cid) are same. Forexample, the base station 101 will have cid 101. Analogously, the basestations 107, 109 and 111 are identified by TAC 20. The base stations107, 109 and 111 together form a cell C2. Furthermore, the base station107, 109 and 111 may be identified by cell identifier (cid) 107, 109 and111, respectively. As shown in FIG. 1A, multiple Tracking Areas mayshare the same EDGE Infra 151. The base stations 101, 103 and 105belonging to TAC 15 and the base stations 107, 109 and 111 belonging toTAC 20 share the same EDGE Infra 151. For example, the applicationssupported by the EDGE Infra 151 may include games like Pokemon Go™ andPUBG™.

With reference to the FIG. 1A, in response to “Registration Request”message from the mobile terminal 100, “Registration Accept” message isreceived from corresponding base station. In the “Registration Accept”message, the mobile terminal 100 will receive LADN information, whichcomprises LADN Access Point Name (LADN APN) and Tracking Area Code (TAC)set. For instance, the mobile terminal 100 will receive LADN APN:{vzw.liquidsky} and Tracking Area Code set, S={15, 20}. Here, ‘vzw’ isthe operator and ‘liquidsky’ is the ESP. When a user with the mobileterminal 100 roams from one cell (C1) to another cell (C2), EDGE trackermodule (to be discussed in FIG. 2) of the mobile terminal 100 checkswhether the TAC of C2 i.e. 20 is present in the set S. If the TAC of C2is present in the set S, the mobile terminal 100 continues with theprevious registration details. Since in this case, the TAC set includes20, the mobile terminal 100 continues with the previous registrationdetails.

In brief, the method of tracking EDGE server by the mobile terminalcomprises of checking, by the mobile terminal, TAC of an another cell ispresent in the TAC set of the mobile terminal when the mobile terminalmoves from one cell to the another cell, and communicating, by themobile terminal, with application server instances using existing EDGEservice IP address and port number, when the TAC of the another cell ispresent in the TAC set of the mobile terminal.

As shown in the FIG. 1B, the environment includes an EDGE Infra 153 anda plurality of base stations 113, 115 and 117 in addition to theenvironment described in the FIG. 1A. Here, the EDGE Infra 153 may referto an EDGE serve or a MEC server. In this example, the applicationsupported by the EDGE Infra 153 may include Pokemon Go™. The basestation may be an evolved Node B (eNodeB) for 4G cellular network or aNext Generation Node B (gNodeB) for 5G cellular network or a basestation supporting 2G and/or 3G technology. The base stations 113, 115and 117 form a TA. The base stations 113, 115 and 117 are identified byTAC 25. The base stations 113, 115 and 117 together form a cell C3.Furthermore, the base station 113, 115 and 117 may be identified by cid113, 115 and 117, respectively.

With reference to the FIG. 1B, when the user with the mobile terminal100 roams from one cell (C1) to another cell (C3), the EDGE trackermodule of the mobile terminal 100 checks whether the Tracking Area Codeof C3 i.e. 25 is present in the set S. If the TAC of C3 is not presentin the set S, the EDGE Tracker of the mobile terminal 100 has tore-register with the ESP. As shown in FIG. 1B, the current TAC is 25,which is not present in TAC set S={15, 20}, hence, the EDGE Tracker ofthe mobile terminal 100 re-registers the mobile terminal 100 with theESP for the usage of new resource EDGE Infra 153.

In brief, the method of tracking EDGE server by the mobile terminalcomprises of re-registering, by the mobile terminal, the mobile terminalinformation with the MEC server using the IP address when the TAC of theanother cell is not present in the TAC set of the mobile terminal.

FIG. 2 shows a block diagram of an architecture of mobile enablementlayer in a mobile terminal in accordance with some embodiments of thepresent disclosure.

The present disclosure uses a mobile terminal 100 that supports anyexisting and upcoming telecommunication technology such as 2G, 3G, 4Gand 5G technology. Here, the mobile terminal 100 may, also, be referredas a terminal, a mobile or a user equipment. The typical features of amobile terminal, for instance, an I/O interface, a display, one or moreprocessors and one or more memories are not described here. In additionto the typical features of the mobile terminal 100, the mobile terminal100 in the present disclosure comprises of a Mobile Enablement Layer(MEL) in Application Framework 203. The MEL may, also, be referred to asEnablement Layer (EL). The terms MEL and EL may be interchangeably usedin the present disclosure. The MEL comprises of following modules: EDGEtracker 2031, Traffic router 2033, DNS proxy 2035 and Service discovery2037. The EDGE tracker module 2031, on receiving “Registration Accept”response, checks the EDGE server availability and fetches LADN APN namealong with a set of Tracking Area Codes (TACs). With the LADN APN name,the EDGE tracker module 2031 identifies the ESP and registers with theESP. The Service discovery module 2037 communicates with the ESP andfinds out EDGE Infra availability and services (application serverinstances) supported at the EDGE Infra. The applications whose serverinstances are available at the EDGE Infra are called EDGE-enabledapplications. The Service discovery module 2037, in turn informs theTraffic router 2033 module, the details of EDGE-enabled applications.From here on, all DNS queries originating from the EDGE-enabledapplications will go to the DNS proxy module 2035. The DNS proxy module2035 receives all the DNS queries initiated by the EDGE-enabledapplications which, in turn, contacts the ESP to find the serveridentity (IP address and port number). The DNS proxy module 2035 thenresponds the DNS queries back with the EDGE service IP address and portnumber. The Traffic router module 2033 routes the DNS requests of theEDGE-enabled applications to the DNS proxy module 2035. For all otherapplications, the DNS traffic goes directly to the operator DNS server.

In addition to MEL, the Application Framework 203 comprises of NetworkManagement Service. The Application Framework 203 is in between Apps 201and Hardware abstraction layer 205 as shown in the FIG. 2. The Hardwareabstraction layer 207 is followed by Kernel 207. The Kernel 207 is anoperating system that allows applications to communicate with hardware.Network Management Service resides in the framework of Android. It is anentity which communicates with Kernel and manages rules related topacket routing. It deals with IP Tables NATing, incoming/outgoingtraffic rules. Hardware Abstraction Layer is the intermediate layerprovided for communication with Kernel. Generally, this Abstractionlayer has User Space APIs to interact with Kernel which runs in Systemor Kernel Space. Kernel is the operating system which provides all theresource management services provided by the OS on the System.

The architecture of mobile enablement layer in a mobile terminal helpsthe application installed in the mobile terminal to find nearest serverinstance without any changes in application code. Finding of the nearestserver instance is irrespective of whether the server instance runs onEDGE infrastructure that uses private IP address or remote/cloudinfrastructure that uses public IP address.

FIG. 3A and FIG. 3B illustrate sequence diagrams explaining operation ofregistration with EDGE server and service discovery by a mobile terminalin a mobile telecommunication network in accordance with someembodiments of the present disclosure.

With reference to the FIG. 3A, step 301 indicates the mobile terminal100 boot completion. At step 303, a “Registration Request” message fromthe mobile terminal 100 is sent to corresponding base station 105, inthis case, gNodeB. In response to the “Registration Request” message,the gNodeB 105 send a “Registration Accept” at step 305 to the mobileterminal 100, which in turn is sent to the MEL of the mobile terminal100 at step 307. In the “Registration Accept” message, the mobileterminal 100 will receive LADN information, which comprises LADN APN andTAC set. For example, in this case, the mobile terminal 100 receivesLADN APN: {vzw.liquidsky} and TAC set={15, 20}. Here, VZW is theoperator and liquidsky is the ESP. The LADN information provided withthe “Registration Accept” message is illustrated in FIG. 7.

Here, the operator shall provide the Data Network Name (DNN). The DNN istypically in the form of an APN. The operator shall provide the DNN nameas vzw.liquidsky, which means ‘vzw’ is the operator and ‘liquidsky’ isthe ESP. Similarly, for example, att.akraino specifies that ‘att’ is theoperator and ‘akraino’ is the ESP. The mobile terminal 100 shall formthe domain name by adding .net to LADN name in order to get (address) ofESP.

At step 309, using the LADN APN, the MEL of the mobile terminal 100sends a DNS query to an operator DNS server. At step 311, the MEL of themobile terminal 100 receives an IP address of ESP from the operator DNSserver. Using the IP address, at step 313, the MEL of the mobileterminal 100 registers the mobile terminal 100 details with the ESP. Themobile terminal 100 details comprise of International Mobile EquipmentIdentity (IMEI), cell identifier (cid), TAC and mobile network operator(MNO). At step 315, the ESP send an acknowledgement for registration tothe MEL of the mobile terminal 100. At step 317, the MEL of the mobileterminal 100 starts a timer. At step 319, the MEL of the mobile terminal100 send a request for getting Fully Qualified Domain Name (FQDN) listof application servers. In response to the request, the ESP sends a listof services/applications supported by MEC server at step 321. At step323, the timer stops after the time expires.

In brief, the operation of registration with EDGE server and servicediscovery by the mobile terminal 100 comprises of transmitting, by themobile terminal, a registration request to a base station, receiving, bythe mobile terminal, a registration accept response from the basestation, wherein the registration accept response comprises LADNinformation, sending, by the mobile terminal, a DNS query using the LADNinformation to a DNS operator, receiving, by the mobile terminal, an IPaddress of a MEC server in response to the DNS query, registering, bythe mobile terminal, mobile terminal information with the MEC serverusing the IP address; and receiving, by the mobile terminal, informationon EDGE infrastructure availability and application server instancesfrom the MEC server.

With reference to the FIG. 3B, step 325 indicates the mobile terminal100 roaming from one cell to another cell and receiving current TAC atstep 327. In this case, the current TAC is 25, which is different fromthe existing TAC set={15, 20} present in the mobile terminal 100. Sincethe current TAC is not present in the existing TAC set, the MEL of themobile terminal 100 re-registers the mobile terminal 100 details withthe ESP at step 329. The mobile terminal 100 details comprise of IMEI,cid, TAC and MNO. At step 331, the ESP send an acknowledgement forregistration to the MEL of the mobile terminal 100. At step 333 the MELof the mobile terminal 100 starts a timer. At step 335, the MEL of themobile terminal 100 send a request (GetFqdnList) for getting new FQDNlist. In response to the request, the ESP sends a list ofservices/applications supported by MEC server at step 337. At step 339,the timer stops after the time expires.

The message format of GetFqdnList is shown below:

app_fqdns {  android_package_name: “com.pokemongo.niantic.net” app_name: “Pokemongo”  app_vers: “1.0”  dev_name: “Niantic Labs” f_q_d_n: “pokemongo.niantic.net” } app_fqdns {  android_package_name:“com.pubg.tencent.net”  app_name: “PUBG”  app_vers: “1.0”  dev_name:“Tencent”  f_q_d_n: “pubg.gaming.net”  f_q_d_n: “pubg.maps.net” }

The above result specifies that there are 2 application supported at theEDGE server: Pokemon Go™ and PUBG™. The parameters within GetFqdnListmessage are as follows:

android_package name: Specifies the unique package name used for Androidspecific platforms. This will be used to notify the user about thepresence of EDGE for a particular application or service.

app_name: User readable Application name.

app_vers: Application version of the app.

dev_name: Specifies the developer name of the application (usually, thecompany which develops the application).

f_q_d_n: Fully Qualified Domain Name used to uniquely identify theservice of an application. Examples include gaming logic, paymentgateways, ad-sense, news pull/push, etc.

In an embodiment, IP address of the ESP may be preconfigured the MEL ofthe mobile terminal 100 or pushed to the MEL of the mobile terminal 100by a DNS operator. The MEL configured in the mobile terminal 100 maytake care of subscription validation on behalf of all the applicationsdeployed/installed on the MEC server. Once the mobile terminal 100 isregistered with the MEC server, the MEL of the mobile terminal 100 maycheck for applications deployed/installed on the MEC server periodically(say once in 2 or 4 or 6 hrs) or/and at every cell change. Thereafter, anotification is provided to all the applications which supports EDGE.The list of application which supports EDGE is stored locally in themobile terminal 100.

In brief, the operation of registration with EDGE server and servicediscovery by the mobile terminal 100 further comprises of receiving, bythe mobile terminal, new information on the EDGE infrastructureavailability and the application server instances from the MEC server ata pre-defined interval of time or at every cell change, and updating, bythe mobile terminal, the stored EDGE infrastructure availability and theapplication server instances with the new information in the internalmemory of the mobile terminal.

In an embodiment, services level granularity for the same applicationmay be achieved using different FQDN's for different services. Forinstance, different modules of the application server may be running ondifferent locations. For example, gaming logic of the PUBG™ gamingapplication, which is latency sensitive, may be placed in the EDGEserver (closer to the user) whereas the advertisement content, which arenot latency sensitive, may come from a remote server. The services levelgranularity is achieved using the FQDN logic explained earlier in FIG.3A and FIG. 3B.

With reference to the FIG. 3C, consider the following case of PUBG™game. The client configuration or application shows 4 FQDNs are used byPUBG™ app. The EDGE server configuration of the same application serverserves only 2 FQDNs, which means that the gaming logic and the maps usedin the game are latency sensitive and kept closer (in the EDGE server)whereas the rarely used information such as advertisements (i.e. ads)will come from the remote server.

FIG. 4 shows a sequence diagram illustrating operation of DNS resolutionand packet routing in a mobile telecommunication network in accordancewith some embodiments of the present disclosure.

In an embodiment, a DNS query is triggered by an application (also,referred as an App) installed in the mobile terminal 100 at the launchof the application at step 401. The EL of the mobile terminal 100detects the DNS query based on destination port set as 53, which may bea fixed destination port. Further, the EL of the mobile terminal 100checks from the DNS query check if the respective application isdeployed/installed on MEC server using MEC application database (App DB)built locally in the mobile terminal 100. In an embodiment, if theapplication is found to be in the MEC App DB, which indicates thepresence of the application on the MEC server, then the following stepsare performed:

At step 403, the EL of the mobile terminal 100 connects the MEC serverto create or initiate application context (Create App Context). In doingso, location information, cell id and FQDN are sent to the MEC server.

At step 405, the MEC server sends an IP address of the FQDN or theapplication server hosted on the MEC server. The EL of the mobileterminal 100 receives the IP address. The same IP address is notified tothe client application by the EL of the mobile terminal 100 at step 407.

At step 409, data session or communication is established between theclient application and application server hosted on the MEC server.

In brief, the operation of DNS resolution and packet routing in a mobiletelecommunication network comprises checking, by the mobile terminal100, whether the EDGE-enabled applications is installed on theapplication server instances based on the DNS query triggered by theEDGE-enabled application and the information stored in the internalmemory of the mobile terminal 100. If the EDGE-enabled application isinstalled on the application server instances, transmitting, by themobile terminal 100, DNS query initiated by EDGE-enabled application inthe mobile terminal 100 to the MEC server for finding EDGE service IPaddress and port number and receiving, by the mobile terminal 100, theEDGE service IP address and port number for the DNS query initiated byEDGE-enabled application in the mobile terminal 100.

In an embodiment, if the application is not found to be in the MEC APPDB, which indicates the absence of the application on the MEC server,then the following steps are performed:

At step 411, the EL of the mobile terminal 100 routes the DNS query to aremote DNS server.

At step 413, the remote DNS server sends an IP address of a remoteserver on a public cloud. The EL of the mobile terminal 100 receives theIP address. The same IP address is notified to the client application bythe EL of the mobile terminal 100.

At step 415, data session or communication is established between theclient application and the remote server on a public cloud.

In brief, if the EDGE-enabled application is not installed on theapplication server instances, transmitting, by the mobile terminal 100,DNS query initiated by EDGE-enabled applications in the terminal 100 tothe DNS operator; and receiving, by the mobile terminal 100, IP addressand port number of a remote server on a public cloud.

FIG. 5 illustrates a sequence diagram explaining operation of verifyinguser location using MEC server in a mobile telecommunication network inaccordance with some embodiments of present disclosure.

In an embodiment, some applications may wish to ensure mobile terminalsthat use a particular application are in specific geographical areas.For example, the specific geographical areas may include a particularcell, a particular city, a particular country or a particular region.There are applications which may send wrong geographical information totheir respective servers. For example, an application may send wrongGlobal Positioning System (GPS) co-ordinates or cell identifier to gainillegal access. Hence, application servers demand a legal way ofverifying user location. The MEC server being deployed close to RadioAccess Network (RAN) can be used to verify user location and give serveraccess to valid users only. This Application Program Interface (API)usage may be provided to all application irrespective of beingdeployed/installed on the EDGE server or not. The EL of the mobileterminal 100 provides generic API interface to verify location.

At first, client application installed in the mobile terminal 100obtains location information at step 501. At step 503, the clientapplication sends “Verify location” request to the EL. The EL of themobile terminal 100 send the “Verify location” request to MEC server atstep 505. The location information may comprise of latitude, longitudeand cell identifier (cell id) details. Thereafter, the MEC servervalidates the location based on techniques which includes, but is notlimited to, triangulation method. The validation is based on comparisonof the location information with latitude and longitude informationshared by the mobile terminal 100. At step 507, the MEC server provides“Verify location” response. The “Verify location” response may compriseaccuracy details based on comparison. On receiving “Verify location”response, the EL sends the “Verify location” response to the clientapplication at step 509.

In brief, the operation of verifying user location using the MEC servercomprising sending, by the mobile terminal 100, verification locationrequest along with latitude, longitude and cell identifier informationof the mobile terminal 100 to the MEC server and receiving, by themobile terminal 100, response to the verification location request fromthe MEC server based on validation. The validation may be based oncomparing location information of the mobile terminal 100 received froma base station and the latitude and longitude information sent by themobile terminal.

The main applications of verifying user location are identityverification and fraud detection. For instance, payment transactionsfrom a credit card may sometimes happen from geographically farlocations. Using this location API, the user will provide cell id,geographical latitude and longitude. The MEC server will verify if theuser is actually attached with the cell and also, makes sure thegeographical latitude and longitude lie within the cell tower region toan acceptable accuracy of 10 m-30 m. With this API, one can make surethat the payment transactions are happening using a mobile terminal. Inthis case, all API calls should go over cellular network. Sometimesinternal GPS can easily be spoofed by 3rd party applications. Using thisAPI, one can make sure that the user's cellular location andgeographical latitude and longitude are almost the same.

For location verification or identity verification, the response latencyshould be less 10 s for payment transactions. This condition can beachieved with the help of location verification server running on theMEC server.

FIG. 6 shows a sequence diagram illustrating operation of APN managementand packet routing in a mobile telecommunication network in accordancewith some embodiments of the present disclosure.

In an embodiment, at launch of an App, the EL of the mobile terminal 100receives notification with the App details from the App Launcher at step601. Here, the Application Launcher is known as Activity Manager.Activity Manager keeps track of states of all applications, likeLaunched, in foreground or in background. The EL of the mobile terminal100 registers with Activity manager to receive notifications forApplication Launch and its state updates. Activity manager then notifiesEL of the mobile terminal 100 about the launch of the applications withtheir details. Here, the App is already installed in the mobile terminal100. From the App details in the notification, the EL of the mobileterminal 100 checks if the respective App is deployed/installed on MECserver using MEC App database (App DB) built locally in the mobileterminal 100. In an embodiment, if the App is found to be in the MEC AppDB, which indicates the presence of the App on the MEC server, then thefollowing steps are performed:

At step 603, the EL of the mobile terminal 100 connects the MEC serverto create or initiate application context (Create App Context). In doingso, location information, cell id and FQDN are sent to the MEC server.

At step 605, the MEC server sends an IP address of the FQDN or theapplication server hosted on the MEC server and APN details from APN DB,which is provided for dedicated APN routing of MEC App. The EL of themobile terminal 100 receives the IP address along with the APN details.The same IP address and the APN details are notified to the App Launcherby the EL of the mobile terminal 100 at step 607.

At step 609, data session or communication is established between theApp Launcher and application server hosted on the MEC server using thededicated MEC APN. Here, the APN details are used for the dedicated MECAPN connection.

In brief, the management of APN and packet routing in a mobiletelecommunication network comprises checking, by the mobile terminal100, whether the EDGE-enabled applications is installed on theapplication server instances based on the DNS query triggered by theEDGE-enabled application and the information stored in the internalmemory of the mobile terminal 100. If the EDGE-enabled application isinstalled on the application server instances, transmitting, by themobile terminal 100, DNS query initiated by EDGE-enabled application inthe mobile terminal 100 to the MEC server for finding EDGE service IPaddress and port number, receiving, by the mobile terminal 100, the EDGEservice IP address and port number and APN information for the DNS queryinitiated by EDGE-enabled application in the mobile terminal 100, andestablishing, by the mobile terminal 100, a data communication channelbetween the mobile terminal 100 and application server hosted on the MECserver using the dedicated MEC APN connection.

In an embodiment, if the App is not found to be in the MEC App DB, whichindicates the absence of the application on the MEC server, then thefollowing steps are performed:

At step 611, the EL of the mobile terminal 100 routes the DNS query to aremote DNS server.

At step 613, the remote DNS server sends an IP address of a remoteserver on a public cloud. The EL of the mobile terminal 100 receives theIP address. The same IP address is notified to the App Launcher by theEL of the mobile terminal 100.

At step 615, data session or communication is established between theApp Launcher and the remote server on a public cloud using default APNconnection. Here, data communication or application traffic is routed todefault internet APN connection.

In brief, if the EDGE-enabled application is not installed on theapplication server instances, transmitting, by the mobile terminal 100,DNS query initiated by EDGE-enabled applications in the terminal 100 tothe DNS operator, receiving, by the mobile terminal 100, IP address andport number of a remote server on a public cloud and establishing, bythe mobile terminal 100, a data communication channel between the mobileterminal 100 and the remote server on a public cloud using default APNconnection.

For instance, suppose PUBG™ is in EDGE-enabled application and Facebookis a non-MEC enabled application. In this case, PUBG™ being MEC enabledapplication will have its data routed using dedicated MEC APN connectionwhereas Facebook being non-EDGE-enabled application will have its datarouted using default internet APN.

In an embodiment, if there is subscription failure or the mobileterminal moves out of operator MEC area, even when the applications haveMEC APN, the data communication or data traffic will be routed viadefault internet APN. These routing decisions are facilitated by the APNmanagement done in the EL of the mobile terminal 100.

The parameter involved in APN management for packet routing aredescribed below:

A database consisting of all app_pkgname_params may be used fordetermining application identifiers (appIds), which are eligible for MECservices in current area. The same parameter may be used for managingapplication data traffic.

A parameter (param_network_subscription_curarea) may be used forchecking for eligibility of the mobile terminal 100 by subscriptionpurchase for MEC services. This may be, also, used for subscriptionmanagement and may be taken into account when EDGE-enabled applicationsare routed via dedicated MEC APN connection.

A parameter (param_roaming_mec) may be used for checking movementin-and-out of MEC coverage area that needs to be tracked for APNmanagement.

Some of the advantages of the present disclosure are listed below.

The present disclosure provides an efficient mechanism for routing datapackets in the telecommunication network based on determining whetherapplication server resides in remote server or EDGE server.

The present disclosure enables to detect EDGE server availability forapplications and provides seamless continuity for the applicationsconnected to the EDGE server during mobility of a terminal.

The present disclosure provides a secure way of verifying user location,thereby, providing server access to valid users.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

The described operations may be implemented as a method, system orarticle of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The described operations may be implemented as code maintainedin a “non-transitory computer readable medium”, where a processor mayread and execute the code from the computer readable medium. Theprocessor is at least one of a microprocessor and a processor capable ofprocessing and executing the queries. A non-transitory computer readablemedium may include media such as magnetic storage medium (e.g., harddisk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs,optical disks, etc.), volatile and non-volatile memory devices (e.g.,EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware,programmable logic, etc.), etc. Further, non-transitorycomputer-readable media include all computer-readable media except for atransitory. The code implementing the described operations may furtherbe implemented in hardware logic (e.g., an integrated circuit chip,Programmable Gate Array (PGA), Application Specific Integrated Circuit(ASIC), etc.).

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary, a variety of optional components are described toillustrate the wide variety of possible embodiments of the invention.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the invention neednot include the device itself.

The illustrated operations of FIGS. 3A, 3B, 4, 5 and 6 show certainevents occurring in a certain order. In alternative embodiments, certainoperations may be performed in a different order, modified or removed.Moreover, steps may be added to the above described logic and stillconform to the described embodiments. Further, operations describedherein may occur sequentially or certain operations may be processed inparallel. Yet further, operations may be performed by a singleprocessing unit or by distributed processing units.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based here on. Accordingly, the disclosure of theembodiments of the invention is intended to be illustrative, but notlimiting, of the scope of the invention, which is set forth in thefollowing claims.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purposes ofillustration and are not intended to be limiting, with the true scopeand spirit being indicated by the following claims.

What is claimed is:
 1. A method for detecting Enhanced Data rates forGlobal System for Mobile (GSM) Evolution (EDGE) server in a mobiletelecommunication network by a mobile terminal, the method comprising:transmitting, by the mobile terminal, a registration request to a basestation; receiving, by the mobile terminal, a registration acceptresponse from the base station, wherein the registration accept responsecomprises Local Area Data Network (LADN) information; sending, by themobile terminal, a Domain Name Server (DNS) query using the LADNinformation to a DNS operator; receiving, by the mobile terminal, anInternet Protocol (IP) address of a Mobile Edge Computing (MEC) serverin response to the DNS query; registering, by the mobile terminal,mobile terminal information with the MEC server using the IP address;and receiving, by the mobile terminal, information on EDGEinfrastructure availability and application server instances from theMEC server.
 2. The method as claimed in claim 1, wherein the LADNinformation comprises at least one of LADN Access Point Name (LADN APN)and tracking area code (TAC) set.
 3. The method as claimed in claim 1,further comprising: storing, by the mobile terminal, the information onEDGE infrastructure availability and application server instances in aninternal memory of the mobile terminal.
 4. The method as claimed inclaim 3, further comprising: receiving, by the mobile terminal, newinformation on the EDGE infrastructure availability and the applicationserver instances from the MEC server at a pre-defined interval of timeor at every cell change; and updating, by the mobile terminal, thestored EDGE infrastructure availability and the application serverinstances with the new information in the internal memory of the mobileterminal.
 5. The method as claimed in claim 3, further comprising:receiving, by the mobile terminal, DNS query triggered by EDGE-enabledapplication in the mobile terminal; checking, by the mobile terminal,whether the EDGE-enabled application is installed on the applicationserver instances based on the DNS query triggered by the EDGE-enabledapplication and the information stored in the internal memory of themobile terminal; if the EDGE-enabled application is installed on theapplication server instances, transmitting, by the mobile terminal, DNSquery initiated by EDGE-enabled application in the mobile terminal tothe MEC server for finding EDGE service IP address and port number; andreceiving, by the mobile terminal, the EDGE service IP address and portnumber for the DNS query initiated by EDGE-enabled application in themobile terminal; if the EDGE-enabled application is not installed on theapplication server instances, transmitting, by the mobile terminal, DNSquery initiated by EDGE-enabled applications in the terminal to the DNSoperator; and receiving, by the mobile terminal, IP address and portnumber of a remote server on a public cloud.
 6. The method as claimed inclaim 3, further comprising: receiving, by the mobile terminal, DNSquery triggered by EDGE-enabled application in the mobile terminal;checking, by the mobile terminal, whether the EDGE-enabled applicationis installed on the application server instances based on the DNS querytriggered by the EDGE-enabled application and the information stored inthe internal memory of the mobile terminal; if the EDGE-enabledapplication is installed on the application server instances,transmitting, by the mobile terminal, DNS query initiated byEDGE-enabled application in the mobile terminal to the MEC server forfinding EDGE service IP address and port number; receiving, by themobile terminal, the EDGE service IP address and port number and AccessPoint Name (APN) information for the DNS query initiated by EDGE-enabledapplication in the mobile terminal; and establishing, by the mobileterminal, a data communication channel between the mobile terminal andthe application server instances using dedicated MEC APN connection; ifthe EDGE-enabled application is not installed on the application serverinstances, transmitting, by the mobile terminal, DNS query initiated byEDGE-enabled applications in the terminal to the DNS operator;receiving, by the mobile terminal, IP address and port number of aremote server on a public cloud; and establishing, by the mobileterminal, a data communication channel between the mobile terminal andthe remote server on a public cloud using default APN connection.
 7. Themethod as claimed in claim 1, further comprising: checking, by themobile terminal, TAC of an another cell is present in the TAC set of themobile terminal when the mobile terminal moves from one cell to theanother cell; communicating, by the mobile terminal, with theapplication server instances using existing EDGE service IP address andport number, when the TAC of the another cell is present in the TAC setof the mobile terminal; and re-registering, by the mobile terminal, themobile terminal information with the MEC server using the IP addresswhen the TAC of the another cell is not present in the TAC set of themobile terminal.
 8. The method as claimed in claim 1, furthercomprising: sending, by the mobile terminal, verification locationrequest along with latitude and longitude information of the mobileterminal to the MEC server; and receiving, by the mobile terminal,response to the verification location request from the MEC server basedon validation, wherein the validation is based on comparing locationinformation of the mobile terminal received from the base station andthe latitude and longitude information sent by the mobile terminal.
 9. Amobile terminal for detecting Enhanced Data rates for Global System forMobile (GSM) Evolution (EDGE) server in a mobile telecommunicationnetwork, the mobile terminal comprising: a processor; and a memorycommunicatively coupled to the processor, wherein the memory storesprocessor-executable instructions, which on execution, cause theprocessor to: transmit a registration request to a base station; receivea registration accept response from the base station, wherein theregistration accept response comprises Local Area Data Network (LADN)information; send a Domain Name Server (DNS) query using the LADNinformation to a DNS operator; receive an Internet Protocol (IP) addressof a Mobile Edge Computing (MEC) server in response to the DNS query;register mobile terminal information with the MEC server using the IPaddress; and receive information on EDGE infrastructure availability andapplication server instances from the MEC server.
 10. The mobileterminal as claimed in claim 9, wherein the LADN information comprisesat least one of LADN Access Point Name (LADN APN) and tracking area code(TAC) set.
 11. The mobile terminal as claimed in claim 9, wherein themobile terminal causes the processor to: store the information on EDGEinfrastructure availability and application server instances in aninternal memory of the mobile terminal.
 12. The mobile terminal asclaimed in claim 11, wherein the mobile terminal causes the processorto: receive new information on the EDGE infrastructure availability andthe application server instances from the MEC server at a pre-definedinterval of time or at every cell change; and update the stored EDGEinfrastructure availability and the application server instances withthe new information in the internal memory of the mobile terminal. 13.The mobile terminal as claimed in claim 11, wherein the mobile terminalcauses the processor to: receive DNS query triggered by EDGE-enabledapplication in the mobile terminal; check whether the EDGE-enabledapplications is installed on the application server instances based onthe DNS query triggered by the EDGE-enabled application and theinformation stored in the internal memory of the mobile terminal; if theEDGE-enabled application is installed on the application serverinstances, transmit DNS query initiated by EDGE-enabled application inthe mobile terminal to the MEC server for finding EDGE service IPaddress and port number; and receive the EDGE service IP address andport number for the DNS query initiated by EDGE-enabled application inthe mobile terminal; if the EDGE-enabled application is not installed onthe application server instances, transmit DNS query initiated byEDGE-enabled applications in the terminal to the DNS operator; andreceive IP address and port number of a remote server on a public cloud.14. The mobile terminal as claimed in claim 11, wherein the mobileterminal causes the processor to: receive DNS query triggered byEDGE-enabled application in the mobile terminal; check whether theEDGE-enabled application is installed on the application serverinstances based on the DNS query triggered by the EDGE-enabledapplication and the information stored in the internal memory of themobile terminal; if the EDGE-enabled application is installed on theapplication server instances, transmit the DNS query initiated byEDGE-enabled application in the mobile terminal to the MEC server forfinding EDGE service IP address and port number; receive the EDGEservice IP address and port number and Access Point Name (APN)information for the DNS query initiated by EDGE-enabled application inthe mobile terminal; and establish a data communication channel betweenthe mobile terminal and the application server instances using dedicatedMEC APN connection; if the EDGE-enabled application is not installed onthe application server instances, transmit the DNS query initiated byEDGE-enabled applications in the terminal to the DNS operator; receiveIP address and port number of a remote server on a public cloud; andestablish a data communication channel between the mobile terminal andthe remote server on a public cloud using default APN connection. 15.The mobile terminal as claimed in claim 9, wherein the mobile terminalcauses the processor to: check TAC of an another cell is present in theTAC set of the mobile terminal when the mobile terminal moves from onecell to the another cell; communicate with the application serverinstances using existing EDGE service IP address and port number, whenthe TAC of the another cell is present in the TAC set of the mobileterminal; and re-register the mobile terminal information with the MECserver using the IP address when the TAC of the another cell is notpresent in the TAC set of the mobile terminal.
 16. The mobile terminalas claimed in claim 9, wherein the mobile terminal causes the processorto: send verification location request along with latitude and longitudeinformation of the mobile terminal to the MEC server; and receiveresponse to the verification location request from the MEC server basedon validation, wherein the validation is based on comparing locationinformation of the mobile terminal received from the base station andthe latitude and longitude information sent by the mobile terminal.